Selective touch scan area and reporting techniques

ABSTRACT

Techniques are disclosed for selective area scanning, touch scanning, and/or reporting of touch screen contacts in electronic touch sensitive devices. The selective area scanning can be used to only scan a specific section of a touch screen area, the selective touch scanning can be used to scan only for specific touches or input sources on a touch screen, and the selective reporting can be used to selectively report only desired contacts to a device processor and reject all other contacts. Multiple selective scan areas can be provisioned, with each discrete area customizable with respect to location, size, accepted touch types and/or reporting criteria. In some cases the user can configure some or all of these selective screen features.

RELATED APPLICATION

This application is a continuation of U.S. application Ser. No. 13/749,410, filed on Jan. 24, 2013 (now U.S. Pat. No. 9,836,154), which is herein incorporated by reference in its entirety.

FIELD OF THE DISCLOSURE

This disclosure relates to electronic display devices, and more particularly, to user input scanning techniques for touch sensitive devices.

BACKGROUND

Electronic display devices such as tablets, eReaders, mobile phones, smart phones, personal digital assistants (PDAs), and other such touch screen electronic display devices are commonly used for displaying consumable content. The content may be, for example, an e-book, an online article or blog, images, documents, an inking or drawing application, a movie or video, just to name a few types. Such display devices are also useful for displaying a user interface that allows a user to interact with files other content on the device. The user interface may include, for example, one or more touch screen controls and/or one or more displayed labels that correspond to nearby hardware buttons. The user may interact with the touch sensitive device using fingers, a stylus, or other implement. The touch screen display may be backlit or not, and may be implemented for instance with an LCD screen or an electrophoretic display. Such devices may also include other touch sensitive surfaces, such as a track pad (e.g., capacitive or resistive touch sensor) or touch sensitive housing (e.g., acoustic sensor).

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1a-b illustrate an example electronic touch sensitive device configured with a selective touch screen function, in accordance with an embodiment of the present invention.

FIGS. 1c-d illustrate example configuration screen shots of the user interface of the electronic touch sensitive device shown in FIGS. 1a-b , configured in accordance with an embodiment of the present invention.

FIG. 2 illustrates a block diagram of an electronic touch sensitive device, configured in accordance with an embodiment of the present invention.

FIGS. 3a-c illustrate example selective touch screen scan regions in an electronic touch sensitive device, in accordance with various embodiments of the present invention.

FIG. 4 illustrates an example configurable touch scan and reporting area of an electronic touch sensitive device, in accordance with an embodiment of the present invention.

FIG. 5a illustrates a method for selective touch scanning and reporting in an electronic touch sensitive device, in accordance with an embodiment of the present invention.

FIG. 5b illustrates another method for selective touch scanning and reporting in an electronic touch sensitive device, in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

Techniques are disclosed for selective area scanning, touch scanning, and/or reporting of touch screen contacts in electronic touch sensitive devices. The selective area scanning can be used to only scan a specific section of a touch screen area, effectively creating dead zones on the touch screen where no user contacts can be detected. The selective touch scanning can also be used to scan only for specific touches or input sources on a touch screen, such as an active stylus input or a finger contact, while rejecting all other types of screen contact. The selective reporting of touch screen contacts can be used to selectively report only desired contacts to a device processor and reject all other contacts. Rejecting unwanted user contacts at the touch screen controller level, before the controller reports to the processor, reduces the burden on the device processor. A selective scan area may also be combined with customized input scanning and reporting features, such that certain areas only scan for or report certain user inputs. Such features can be used to reduce power consumption and may increase device performance by reducing the burden on the device processor. In some cases the user can configure some or all of these selective screen features, while in other cases the selective screen features are hard-coded or set by default.

General Overview

As previously explained, electronic display devices such as tablets, eReaders, and smart phones are commonly used for displaying user interfaces and consumable content. In some instances the user might desire to interact with the device in only using a stylus, or only a finger. In other instances the user might wish for the touch sensitive surface to only register screen taps and not sweeping gestures, or vice versa. In still other instances, the user might wish for a touch screen to only register contacts in a certain area of the screen, only register sweeping gestures in certain areas of the screen, or not register or scan for any inputs in a certain area of the screen. While some electronic devices provide hand-rejection techniques, or reject certain stray contacts on a touch sensitive surface, such techniques involve scanning the entire touch sensitive surface, registering the undesired input, analyzing the input at the processor to determine that it is an undesired input, and rejecting the input. Such techniques create undesired burden on the processor and waste valuable resources in scanning for, analyzing, and rejecting undesired inputs. There does not appear to be an effective and power-saving selective touch scanning and reporting function for electronic touch sensitive devices.

Thus, and in accordance with an embodiment of the present invention, techniques are provided for selectively scanning and reporting inputs in an electronic touch sensitive device. The techniques disclosed may be used to customize the touch screen of a device to only scan specific areas, to selectively scan certain areas, or to selectively report user contacts to the processor. In some embodiments, the user may identify a dead zone, or a no-scan zone, where the touch screen controller does not scan for any user inputs. If no inputs are desired in that area, device performance may increase by not unnecessarily scanning such an area. In other embodiments, the user may identify a selective scan area where only certain inputs are scanned for, such as inputs from an active stylus. In such a case, the user does not care about other inputs and device performance may increase by only scanning for a desired input source. In still other embodiments, the user may wish to scan for all or some input sources but may only be interested in specific gestures, such as a sweeping gesture. In such a case, the touch screen controller may report sweeping gestures to the processor and reject all other gestures (such as a tap gesture) before reporting to the device processor. In still other embodiments, unwanted input sources may also be identified and discarded at the controller level if the screen is scanned for all input sources. In such an example embodiment, the screen may scan for all input sources but report only finger contacts while discarding active stylus inputs. Many other configurations and variations of these selective scan and/or reporting features will be apparent in light of this disclosure.

Note that any touch sensitive device (e.g., track pad, touch screen, or other touch sensitive surface, whether capacitive, resistive, acoustic or other input detecting technology) may be used to selectively detect the user input and the claimed invention is not intended to be limited to any particular type of touch sensitive technology, unless expressly stated.

Architecture

FIGS. 1a-b illustrate an example electronic touch sensitive device with a selective touch scanning and reporting function, configured in accordance with an embodiment of the present invention. The device could be, for example, a tablet such as the NOOK® tablet by Barnes & Noble. In a more general sense, the device may be any electronic device having a touch sensitive user interface and capability for displaying content to a user, such as a mobile phone or mobile computing device such as an eReader or laptop, a desktop computing system, a television, a smart display screen, or any other device having a touch screen display or a non-touch display screen that can be used in conjunction with a touch sensitive surface. As will be appreciated, the claimed invention is not intended to be limited to any particular kind or type of electronic device.

The touch screen display (or touch sensitive screen) can be any display that is configured with user input detecting technologies, whether capacitive, resistive, acoustic, active-stylus, and/or other input detecting technology. The screen display can be layered above input sensors, such as a capacitive sensor grid (e.g., for passive touch-based input, such as with a finger or passive stylus in the case of a so-called in-plane switching (IPS) panel), or an electro-magnetic resonance (EMR) sensor grid (e.g., for active stylus-based input). In some embodiments, the touch screen display can be configured with a purely capacitive sensor, while in other embodiments the touch screen display may be configured to provide a hybrid mode that allows for both capacitive input and active stylus input. In still other embodiments, the touch screen display is configured with only an active stylus sensor. Numerous touch screen display configurations can be implemented using any number of known or proprietary screen based input detecting technology. In any such embodiments, a touch screen controller may be configured to selectively scan the touch screen display and/or selectively report contacts detected directly on or otherwise sufficiently proximate to (e.g., within a few centimeters) the touch screen display. Thus, in some such embodiments, the touch screen controller can be configured to interpret inputs from only a capacitive input, only an active stylus input, or both.

As previously explained, the user input may be provided, for example, by a passive implement (e.g., finger or capacitive stylus) or an active stylus, depending on the configuration of the touch screen display. In one example embodiment, an active stylus input can be provided by an actual physical contact on a touch sensitive surface. However, in other embodiments, the active stylus input may involve the stylus hovering some distance above the touch screen display surface (e.g., one to a few centimeters above the surface, or even farther, depending on the sensing technology deployed in the touch screen display), but nonetheless triggering a response at the device just as if direct contact were provided. As will be appreciated in light of this disclosure, an active stylus as used herein may be implemented with any number of active stylus technologies, such as DuoSense® pen by N-trig® (e.g., wherein the active stylus utilizes a touch sensor grid of a touch screen display) or EMR-based pens by Wacom technology, or any other commercially available or proprietary active stylus technology. Further recall that the active stylus sensor in the computing device may be distinct from an also provisioned touch sensor grid in the computing device. Having the touch sensor grid separate from the active stylus sensor grid allows the device to, for example, only scan for an active stylus input, a touch contact, or to scan specific areas for specific input sources, in accordance with some embodiments. In one such embodiment, the active stylus sensor grid includes a network of antenna coils that create a magnetic field which powers a resonant circuit within the active stylus. In such an example, the active stylus may be powered by energy from the antenna coils in the device and the stylus may return the magnetic signal back to the device, thus communicating the stylus' location, angle of inclination, speed of movement, etc. Such an embodiment also eliminates the need for a battery on the stylus.

As can be seen with this example configuration, the device comprises a housing that includes a number of hardware features such as a power button, control features, and a press-button (sometimes called a home button herein). A touch screen based user interface is also provided, which in this example embodiment includes a quick navigation menu having six main categories to choose from (Home, Library, Shop, Search, Light, and Settings) and a status bar that includes a number of icons (a night-light icon, a wireless network icon, and a book icon), a battery indicator, and a clock. Other embodiments may have fewer or additional such user interface (UI) touch screen features, or different UI touch screen features altogether, depending on the target application of the device. Any such general UI controls and features can be implemented using any suitable conventional or custom technology, as will be appreciated.

The hardware control features provided on the device housing in this example embodiment are configured as elongated press-bars and can be used, for example, to page forward (using the top press-bar) or to page backward (using the bottom press-bar), such as might be useful in an eReader application. The power button can be used to turn the device on and off, and may be used in conjunction with a touch-based UI control feature that allows the user to confirm a given power transition action request (e.g., such as a slide bar or tap point graphic to turn power off). Numerous variations will be apparent, and the claimed invention is not intended to be limited to any particular set of hardware buttons or features, or device form factor.

In this example configuration, the home button is a physical press-button that can be used as follows: when the device is awake and in use, tapping the button will display the quick navigation menu, which is a toolbar that provides quick access to various features of the device. The home button may also be configured to cease an active function that is currently executing on the device, or close a configuration sub-menu that is currently open. The button may further control other functionality if, for example, the user presses and holds the home button. For instance, an example such push-and-hold function could engage a power conservation routine where the device is put to sleep or an otherwise lower power consumption mode. So, a user could grab the device by the button, press and keep holding as the device was stowed into a bag or purse. Thus, one physical gesture may safely put the device to sleep. In such an example embodiment, the home button may be associated with and control different and unrelated actions: 1) show the quick navigation menu; 2) exit a configuration sub-menu; and 3) put the device to sleep. As can be further seen, the status bar may also include a book icon (upper left corner). In some cases, tapping the book icon may provide bibliographic information on the content or provide the main menu or table of contents for the book, movie, playlist, or other content.

In one example embodiment, a selective touch screen configuration sub-menu, such as the one shown in FIG. 1d , may be accessed by tapping or otherwise selecting the Settings option in the quick navigation menu, which causes the device to display the general sub-menu shown in FIG. 1c . From this general sub-menu, the user can select any one of a number of options, including one designated Screen in this specific example case. Selecting this sub-menu item (with an appropriately placed screen tap) may cause the configuration sub-menu of FIG. 1d to be displayed, in accordance with an embodiment. In other example embodiments, selecting the Screen option may present the user with a number of additional sub-options, one of which may include a so-called selective touch screen function option, which may then be selected by the user so as to cause the selective touch screen configuration sub-menu of FIG. 1d to be displayed. Any number of such menu schemes and nested hierarchies can be used, as will be appreciated in light of this disclosure. In other embodiments, the selective touch screen function is hard-coded such that no configuration sub-menus are needed or otherwise provided (e.g., an application specific selective touch screen as described herein, with no user configuration).

As will be appreciated, the various UI control features and sub-menus displayed to the user are implemented as UI touch screen controls in this example embodiment. Such UI touch screen controls can be programmed or otherwise configured using any number of conventional or custom technologies. In general, the touch screen translates the user touch in a given location into an electrical signal which is then received and processed by the underlying operating system (OS) and circuitry (processor, etc). The user touch may be performed with a finger, a stylus, or any other suitable implement, unless otherwise specified. Additional example details of the underlying OS and circuitry in accordance with some embodiments will be discussed in turn with reference to FIG. 2.

As previously explained, and with further reference to FIGS. 1c and 1d , once the Settings sub-menu is displayed (FIG. 1c ), the user can then select the Screen option. In response to such a selection, the selective scan/reporting configuration sub-menu shown in FIG. 1d can be provided to the user. The user can configure a number of features with respect to the selective area scanning and reporting feature, in this particular example. In this example case, the configuration sub-menu includes a UI check box that when checked, or otherwise selected by the user, effectively enables the selective touch screen mode (shown in the enabled state); unchecking the box disables the mode. Other embodiments may have the selective touch screen mode always enabled, while in other embodiments the mode may be enabled or disengaged by a physical switch or button, or by a uniquely identifiable gesture or screen contact, for example.

In this example embodiment the user can select, with a UI check box, a ‘Custom Input’ that is to be scanned for or reported by the touch sensitive surface. As can be further seen with reference to FIG. 1d , examples of possible custom inputs that may be scanned for and reported include ‘Only Finger’ inputs, ‘Only Stylus’ inputs, ‘Only Tap’ inputs, or ‘Only Gesture’ inputs. In some embodiments, the touch screen controller can scan only a determined section of the touch screen, thus creating a dead zone in non-scanned sections where no user input is scanned for. In other embodiments, the controller may selectively scan for specific inputs, such as a finger contact or an active stylus contact. In still other embodiments, the touch screen controller may analyze user contact and only report certain inputs to the processor, thus rejecting unwanted user input without using additional processor resources. In such an example, the user may only be interested in sweeping gestures in a certain area, and the controller may be programmed to only report sweeping gestures to the processor while rejecting tap gestures. This provides much more efficiency compared to analyzing and rejecting unwanted user inputs at the processor or application level. Multiple combinations and variation of these embodiments will be apparent in light of this disclosure.

In some embodiments, the user may specify a number of applications or scenarios in which the selective touch screen mode can be enabled. Such a configuration feature may be helpful, for instance, in a tablet or laptop or other multifunction computing device that can execute different applications (as opposed to a device that is more or less dedicated to a particular application). In this example case, the available applications are provided along with a corresponding check box as shown in FIG. 1d . Note the diverse nature of the examples, including an ‘eBook’ application, a ‘Word Processor’ application, a ‘Drawing’ application, a ‘Video Player’ application, and the ‘Lock Mode’ which are just a few examples. Any number of applications or device functions may benefit from a selective touch screen mode as provided herein, whether user-configurable or not, and the claimed invention is not intended to be limited to any particular application or set of applications. In this particular example shown in FIG. 1d , the selective touch screen mode is enabled for drawing and video player applications, as well as the lock mode.

As previously explained, the user may specify a number of custom inputs that are to be scanned for or selectively reported to the processor. Such a configuration feature may be helpful, for example, if the user is only interested in inputs from an active stylus, or a specific stylus. In such an example, the touch screen controller can selectively scan only for inputs from the active stylus and ignore any other contacts made on the touch screen. Such a configuration feature may also be helpful if the user wishes to scan an area for stylus inputs, for example, but is only interested in sweeping gestures. In such an example, the touch screen controller can scan for stylus inputs but only report sweeping gestures to the processor, rejecting all other stylus contacts at the controller level without consuming any processor resources. In this particular example case, the custom inputs of ‘Only Stylus’ and ‘Only Gesture’ inputs have been selected. In such an example, the screen controller may only scan for active stylus inputs, and the controller will only report stylus gestures to the processor while rejecting stylus taps before reporting to the processor. In another such example, the controller may scan the selective touch screen area for all inputs but reject non-stylus inputs at the controller level rather than perform a selective scan.

In addition, a back button arrow UI control feature may be provisioned on the touch screen, so that the user can go back to the Settings menu after the selective touch screen function has been configured, if so desired. While a number of user-configurable features are provided in some embodiments, other embodiments may have any combination of similar features wherein the features are set as a given default or are otherwise hard-coded, such that no user configuration is necessary.

FIG. 2 illustrates a block diagram of an electronic touch screen device configured in accordance with an embodiment of the present invention. As can be seen, this example device includes a processor, memory (e.g., RAM and/or ROM for processor workspace and storage), additional storage/memory (e.g., for content), a communications module, a touch screen with a touch screen controller, and an audio module. A communications bus and interconnect is also provided to allow inter-device communication. Other typical componentry and functionality not reflected in the block diagram will be apparent (e.g., battery, co-processor, etc). In any such cases, the touch screen surface is generally capable of translating a user's physical contact with the surface into an electronic signal that can be manipulated or otherwise used to trigger a specific user interface action, such as those provided herein. As stated previously, the principles provided herein equally apply to any touch screen device.

In this example embodiment, the memory includes a number of modules stored therein that can be accessed and executed by the processor (and/or a co-processor). The modules include an operating system (OS), a user interface (UI), and a power conservation routine (Power). The various modules can be implemented, for example, in any suitable programming language (e.g., C, C++, objective C, JavaScript, custom or proprietary instruction sets, etc), and encoded on a machine readable medium, that when executed by the processor (and/or co-processors), carries out the functionality of the device. Other embodiments can be implemented, for instance, with gate-level logic or an application-specific integrated circuit (ASIC) or chip set or other such purpose built logic, or a microcontroller having input/output capability (e.g., inputs for receiving user inputs and outputs for directing other components) and a number of embedded routines for carrying out the device functionality. In short, the functional modules can be implemented in hardware, software, firmware, or a combination thereof.

The processor can be any suitable processor (e.g., 800 MHz Texas Instruments OMAP3621 applications processor), and may include one or more co-processors or controllers to assist in device control. In this example case, the processor receives input from the user, including input from or otherwise derived from the power button and the home button. The processor can also have a direct connection to a battery so that it can perform base level tasks even during sleep or low power modes. The memory (e.g., for processor workspace and executable file storage) can be any suitable type of memory and size (e.g., 256 or 512 Mbytes SDRAM), and in other embodiments may be implemented with non-volatile memory or a combination of non-volatile and volatile memory technologies. The storage (e.g., for storing consumable content and user files) can also be implemented with any suitable memory and size (e.g., 2 GBytes of flash memory). The display can be implemented, for example, with a 6-inch E-ink Pearl 800×600 pixel screen with Neonode® zForce® touch screen, or any other suitable display and touch screen interface technology. The communications module can be, for instance, any suitable 802.11 b/g/n WLAN chip or chip set which allows for connection to a local network so that content can be downloaded to the device from a remote location (e.g., content provider, etc., depending on the application of the display device). In some specific example embodiments, the device housing that contains all the various componentry measures about 6.5″ high by about 5″ wide by about 0.5″ thick, and weighs about 6.9 ounces. Any number of suitable form factors can be used, depending on the target application (e.g., laptop, desktop, mobile phone, etc). The device may be smaller, for example, for smartphone and tablet applications and larger for smart computer monitor applications.

The operating system (OS) module can be implemented with any suitable OS, but in some example embodiments is implemented with Google Android OS or Linux OS or Microsoft OS or Apple OS. As will be appreciated in light of this disclosure, the techniques provided herein can be implemented on any such platforms. The power management (Power) module can be configured as typically done, such as to automatically transition the device to a low power consumption or sleep mode after a period of non-use. A wake-up from that sleep mode can be achieved, for example, by a physical button press and/or a touch screen swipe or other action. The user interface (UI) module can be, for example, based on touch screen technology and the various example screen shots shown in FIGS. 1a-d, 3a-c , and 4, in conjunction with the selective touch screen methodologies demonstrated in FIGS. 5a-b , which will be discussed in turn. The audio module can be configured, for example, to speak or otherwise aurally present a selected eBook table of contents or other textual content, if preferred by the user. Numerous commercially available text-to-speech modules can be used, such as Verbose text-to-speech software by NCH Software. In some example cases, if additional space is desired, for example, to store digital books or other content and media, storage can be expanded via a microSD card or other suitable memory expansion technology (e.g., 32 GBytes, or higher).

The touch screen controller can be any suitable controller (e.g. the CYP658756 chip by Cypress), with sufficient hardware control to implement the selective scan area features disclosed herein, and sufficient software to implement the selective scanning and reporting features. The touch screen controller may be local to the touch screen in some embodiments and may selectively scan, analyze, and/or selectively report touch screen inputs to the processor via the communications bus. The touch screen controller works with and reports to the processor, and although some inputs may be analyzed and rejected at the controller level, other functions may be performed at the processor if needed or otherwise desired. In other embodiments, the touch screen controller may also be in communication with an application currently running on a device, such that the controller may scan a custom area, or selectively report custom inputs based on which application the user is running at that moment. As will be appreciated in light of this disclosure, analyzing and selectively discarding and reporting inputs at the controller level can save power and processor resources, thus providing a more efficient touch sensitive computing system.

Selective Touch Screen Examples

FIG. 3a illustrates an example selective touch screen mode of an electronic touch sensitive device, in accordance with an embodiment of the present invention. As can be seen, a physical frame or support structure is provided about the screen of the device. As can be further seen in this example, the screen area contains a selective touch screen (or inking) area, shown as the shaded area of the touch screen, and a secondary touch screen area on the upper and left borders of the touch screen. In one particular application of the present invention, the user has opened an inking application and only wishes to register stylus inputs/gestures in the inking area of the screen. In one such example configuration, the inking area can be a stylus-selective touch screen area (shown as the shaded section of the touch screen), while the secondary touch screen area (shown as the non-shaded section of the touch screen) can be scanned normally and all user inputs are registered and analyzed. This may be useful if the user wishes to only mark with a stylus within the drawing page of an inking application. In such an example, any stray hand contacts or tap inputs will not be registered/reported or otherwise affect the inking area of the screen.

In other embodiments, the secondary touch screen area of the screen may also selectively scan or report user inputs. In such an example, the upper and left borders of the touch screen may only scan or only report finger taps, while the inking area only scans or reports stylus gestures. In one embodiment, the selective touch screen area is implemented by only scanning for stylus inputs within the selective touch screen area. In another embodiment, the selective screen area is implemented by having the touch screen controller discard all unwanted user inputs and only reporting certain inputs to the processor. Such embodiments conserve power and processor resources by selective scanning, or by discarding unwanted contacts at the touch screen controller level.

In some embodiments, either the selective touch screen area or the secondary touch screen area may be configured to scan for or report any number of user inputs. For example, the areas may be configured to only scan for finger inputs or stylus inputs, or they may be configured to only report taps, swipes, stylus inputs, multi-point contacts, etc. to the processor. In still other embodiments, either of the selective touch screen area or the secondary touch screen area may be configured as a dead zone that accepts no user input. Any number of combinations of scanning and reporting features may be implemented and will be apparent in light of this disclosure.

FIG. 3b illustrates another example selective touch screen mode of an electronic touch sensitive device, in accordance with an embodiment of the present invention. This particular example may be suitable for a lock mode selective scanning technique, wherein only a portion of the screen is scanned for user input while the rest of the screen is a dead zone. Such an embodiment may conserve power and processor resources by only scanning the area designed to detect an unlock UI gesture. As seen in this example, the touch screen area includes a scan area on the bottom of the screen, shown as the shaded area of the touch screen. The remainder of the touch screen area is a no-scan area. The scan and no-scan areas may be configured by the user to custom sizes and inputs, as discussed earlier, or they may be hard coded and not configurable. The context of this example case is for a lock mode feature at the bottom of a touch screen area (such as a slide bar touch screen UI feature), but numerous other context-specific embodiments will be appreciated in light of this disclosure. For instance, in another example embodiment, the scan and no-scan areas are configured for use with a text messaging application, wherein only the keyboard and text entry areas are scanned and all other areas are no-scan areas.

FIG. 3c illustrates another example selective touch screen mode of an electronic touch sensitive device, in accordance with an embodiment of the present invention. As can be seen, this particular example shows a large no-scan area in the center of the touch screen, shown as the shaded area of the touch screen. This large no-scan area is bordered on the top and the bottom by areas of the touch screen that are scanned normally for user inputs, in this example embodiment. Stray taps on a video screen may cause an unwanted pause or rewind in a movie, and this particular selective touch screen configuration may be useful, for example, for a video player application, where inputs are only expected at the control bar (e.g., pause, play, stop, rewind, etc) and/or volume control area of the video player. In addition to creating a more convenient viewing experience, the selective scanning can increase device performance and battery life.

FIG. 4 illustrates an example configurable touch scan and reporting area of an electronic touch sensitive device, in accordance with an embodiment of the present invention. As can be seen, this particular example shows a shaded selective touch screen area substantially in the center of the touch screen. On the upper and left borders of the touch screen, a custom scan area grid or ruler is provided in this example, along with a number of scan boundary markers/handles that can be adjusted to customize the size of the scan area. In this particular example, the selective touch screen area may be adjusted to a custom size by relocating the various scan boundary markers. In such an example, the selective touch screen area may be associated with one or more applications, with a selective scan function, a selective input reporting function, a no-scan function, or any combination of the previously discussed selective touch screen features. In some embodiments, multiple such configurable selective touch screen areas may be identified on a single touch screen surface, each having customized scanning and reporting features. As previously explained, the described techniques may be user-configurable or hard-coded. To this end, note that the number of configurable scan areas may be user-configurable. Thus, if the user configures the device to have two configurable scan areas, for instance, then two distinct scan areas would be provisioned, each having a set of adjustable boundary markers so as to allow for full customization with respect to size, location, scanning, and reporting.

Methodologies

FIGS. 5a-b illustrates a method for selective touch sensitive scanning and reporting in an electronic touch screen device, in accordance with an embodiment of the present invention. This example methodology may be implemented, for instance, by the touch screen controller of the touch sensitive electronic device shown in FIG. 2. To this end, the touch screen controller module can be implemented in software, hardware, firmware, or any combination thereof, as will be appreciated in light of this disclosure.

In general, any touch sensitive device may be used to detect user contact. As soon as the user begins to drag or otherwise move a finger or stylus tip, the touch screen controller code (and/or hardware) can assume a drag gesture has been engaged and track the path of the user contact with respect to any fixed point within the touch surface until the user stops engaging the touch screen surface. The release point can also be captured by the controller as it may be used to commit the action started when the stylus pressed on the touch sensitive surface. In a similar fashion, if the user releases the contact without moving the finger or stylus tip, a tap or press or press-and-hold command may be assumed depending on the amount of time the user was continually pressing on the touch sensitive surface. These main detections can be used in various ways to implement UI functionality.

In the example shown in FIG. 5a , the method includes determining 501 whether the selective touch screen mode is enabled. If not, then the screen surface may be scanned 502 normally. If the selective touch screen mode is enabled, the method may continue with determining 503 whether a custom touch screen area is enabled. A custom touch screen area may be any area other than the entire touch screen area and such a custom touch screen area may be configurable by the user, default touch screen area settings may be associated with specific applications, or they may be hard-coded. Also, multiple custom touch screen areas may be present on the touch screen of a single device. If a custom touch screen area is selected, the method may continue with determining 504 whether a custom input scan is enabled. Similarly with the custom touch screen area, the custom input scan feature may be configurable by the user, it may have a default setting associated with specific applications, or it may be hard coded into the device. If a custom input scan is enabled, then the method may continue with scanning 508 the selected area of the touch screen only for a selected input. One example of such a scan would be to scan only a section of the screen for an active stylus input. If no custom input scan is selected, then the method may continue with determining 505 whether custom input reporting is enabled. Custom input reporting is distinct from custom input scanning because an input is scanned for and rejected by the screen controller, rather than not being scanned for at all. If custom input reporting is enabled, the method may continue with scanning 507 the selected area of the touch screen and selectively reporting to the processor the desired inputs, while discarding all other inputs detected. If no custom input reporting is enabled, the method may continue with scanning 506 the selected touch screen area for all user inputs.

If, however, a custom touch screen area is not selected at 503, the method may continue with determining 509 whether a custom input scan is selected for the entire touch screen. If a custom input scan is selected, the method may continue with scanning 511 the entire screen area for the selected user input. If no custom input scan is selected, the method may continue with determining 510 whether custom input reporting is enabled. If custom input reporting is enabled, the method may continue with scanning 512 the entire screen area and selectively reporting to the processor only the desired inputs, while discarding all other inputs detected. If no custom input reporting is enabled, the method may continue with scanning 502 the surface normally. The various features and functions descried above may be configured in a configuration sub-menu, like the one shown in FIG 1d , or they may be hard coded as previously explained.

FIG. 5b illustrates another method for selective touch scanning and reporting in an electronic touch sensitive device, in accordance with an embodiment of the present invention. In this example case, the method also includes determining 501 whether the selective touch screen mode is enabled. If not, then the screen surface may be scanned 502 normally. If the selective touch screen mode is enabled, the method may continue with determining 503 whether a custom touch screen area is enabled. A custom touch screen area may be any area other than the entire touch screen area and such a custom touch screen area may be configurable by the user, default touch screen area settings may be associated with specific applications, or they may be hard-coded. Also, multiple custom touch screen areas may be present on the touch screen of a single device. If a custom touch screen area is selected, the method may continue with scanning 520 the one or more selected/active screen areas. The method may then continue with reporting 521 selected user inputs for each active screen area. The inputs that are reported for each active screen area may be configurable, or may be hard coded in the device. If no custom touch screen area is selected, the method may continue with scanning 522 the entire screen area. The method may then continue with reporting 523 selected user inputs; and as discussed above, the inputs that are reported may be configurable or hard coded in the device.

The foregoing description of the embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of this disclosure. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. 

What is claimed is:
 1. An electronic device, comprising: a touch screen display for displaying content to a user and having an input detecting area configured to receive user inputs; and a touch screen controller having a selective touch screen mode configured to selectively scan the touch screen display by scanning for user input from a preselected portion of the input detecting area that is not all of the input detecting area of the touch screen display; and a user interface configured to present a set of adjustable boundary markers to allow for user-customization of the preselected portion of the input detecting area with respect to size and location of the preselected portion.
 2. The device of claim 1 wherein the user interface further includes a custom scan area ruler to indicate position of the set of adjustable boundary markers on the input detecting area, which in turn indicates the position of the preselected portion.
 3. The device of claim 1 wherein the touch screen display includes multiple preselected portions of the input detecting area, each of the multiple preselected portions being associated with a set of adjustable boundary markers.
 4. The device of claim 1, wherein the touch screen display includes a no-scan area, the no-scan being a portion of the input detecting area that is outside of the preselected portion and where scanning for user input is not performed.
 5. The device of claim 1, wherein the preselected portion of the input detecting area is configured for use with an application, such that a text entry area and/or a user interface control feature of the application is presented within the preselected portion.
 6. The device of claim 1, wherein inputs received outside the preselected portion are ignored.
 7. The device of claim 1, wherein only a subset of inputs detectable via the touch screen display and that are received within the preselected portion of the display are reported, such that one or more of the inputs detectable via the touch screen display that are received within the preselected portion of the display reported are not reported.
 8. The device of claim 1, wherein the preselected portion is a first preselected portion, and the input detecting area further includes a second preselected portion.
 9. The device of claim 8, wherein the second preselected portion of the input detecting area is associated with one or more of a selective scan function, a selective reporting function, and/or a no-scan function.
 10. The device of claim 8, wherein the touch screen controller is further configured to selectively scan the second preselected portion for an input gesture or input source that is not scanned for in the first preselected portion.
 11. A system, comprising: a processor; a touch screen display for displaying content to a user and having an input detecting area, the touch screen display allowing a plurality of user input gesture types from a plurality of user input sources; a user interface configured to present a set of adjustable boundary markers to allow for user-customization of a preselected portion of the input detecting area with respect to size and location of the preselected portion; and a touch screen controller having a selective touch screen mode configured to at least one of selectively scan or report a subset of inputs detectable via the touch screen display and that are received within the preselected portion of the display, such that one or more of the inputs detectable via the touch screen display that are received within the preselected portion of the display reported are not scanned for or reported to the processor.
 12. The system of claim 11, wherein the subset of inputs that are selectively scanned for or reported include an unlock screen gesture or an unlock user interface gesture.
 13. The system of claim 11, wherein inputs received outside the preselected portion are ignored.
 14. The system of claim 11, wherein the preselected portion is a first preselected portion, and the input detecting area further includes a second preselected portion, wherein the second preselected portion is associated with one or more of a selective scan function, a selective reporting function, and/or a no-scan function.
 15. The system of claim 11 wherein the subset of inputs selectively scanned for or reported to the processor is user-configurable with respect to one or more of input source and/or gesture type.
 16. A non-transitory computer readable medium encoded with instructions that when executed by one or more processors, cause a process to be carried out in a system having a touch screen display, the touch screen display having an input detecting area and configured for detecting user input, the process comprising: presenting a user interface configured to present a set of adjustable boundary markers so as to allow for user-customization of a preselected portion of the input detecting area with respect to size and location of the preselected portion, wherein the preselected portion is not all of the input detecting area of the touch screen display; and selectively scanning the touch screen display by scanning for input from the preselected portion of the input detecting area, such that there is a portion of the input detecting area where scanning for input is not performed.
 17. The computer readable medium of claim 16 wherein the preselected portion is a first preselected portion, and the input detecting area further includes a second preselected portion, and wherein selectively scanning the touch screen display further includes scanning for input from the second preselected portion for input different than input scanned for in the first preselected portion.
 18. The computer readable medium of claim 16, wherein prior to selectively scanning, the process further comprises: receiving boundary input based on manipulation of the adjustable boundary markers, the boundary input specifying the size and the location of the preselected portion; and establishing the preselected portion of the input detecting area at the specified location.
 19. The computer readable medium of claim 16 wherein only a subset of inputs detectable via the touch screen display and that are received within the preselected portion of the display are reported, such that one or more of the inputs detectable via the touch screen display that are received within the preselected portion of the display reported are not reported.
 20. The computer readable medium of claim 16 wherein inputs received outside the preselected portion are ignored. 